Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change allowed FQDN for ADConnect endpoints #1505

Merged

Conversation

craddm
Copy link
Contributor

@craddm craddm commented Jul 17, 2023

✅ Checklist

  • You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
  • You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
  • Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).
  • You have marked this pull request as a draft and added '[WIP]' to the title if needed (if you're not yet ready to merge).
  • You have formatted your code using appropriate automated tools (for example ./tests/AutoFormat_Powershell.ps1 -TargetPath <path to file or directory> for Powershell).

⤴️ Summary

Changes the FQDN that represents ADConnect endpoints used in a remote Powershell script. Previously, many individual endpoints were listed in the SHM firewall rules, which were captured by g*.servicebus.windows.net. The pattern needed to be changed.

In addition, when running the remote test scripts for external DNS queries, the script now only retrieves VM names from the appropriate resource group in the SHM/SRE, rather than finding any VM in the whole subscription with a matching IP address.

🌂 Related issues

Closes #1503
Closes #1507

🔬 Tests

Tested on existing and new deployments of SREs

@craddm craddm closed this Jul 17, 2023
@craddm craddm reopened this Jul 17, 2023
@craddm craddm marked this pull request as draft July 17, 2023 11:50
@@ -81,7 +81,8 @@ Add-LogMessage -Level Info "Looking for SRD with IP address '$vmIpAddress'..."
if (-not $vmIpAddress) {
Add-LogMessage -Level Fatal "No SRD found with IP address '$vmIpAddress'. Cannot run test to confirm external DNS resolution."
} else {
$vmName = @(Get-AzNetworkInterface | Where-Object { $_.IpConfigurations.PrivateIpAddress -eq $vmIpAddress } | ForEach-Object { $_.VirtualMachine.Id.Split("/")[-1] })[0]
# Match on both IP address and resource group
$vmName = @(Get-AzNetworkInterface | Where-Object { $_.IpConfigurations.PrivateIpAddress -eq $vmIpAddress -and $_.ResourceGroupName -eq $config.sre.srd.rg } | ForEach-Object { $_.VirtualMachine.Id.Split("/")[-1] })[0]
Copy link
Member

@jemrobinson jemrobinson Jul 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a -ResourceGroupName argument to Get-AzNetworkInterface to simplify the logic if you'd like.

@craddm craddm changed the title [WIP] Change allowed FQDN for ADConnect endpoints Change allowed FQDN for ADConnect endpoints Jul 21, 2023
@craddm craddm marked this pull request as ready for review July 21, 2023 14:00
Copy link
Member

@jemrobinson jemrobinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jemrobinson jemrobinson merged commit d246c31 into alan-turing-institute:develop Jul 26, 2023
9 of 10 checks passed
@jemrobinson jemrobinson mentioned this pull request Aug 14, 2023
5 tasks
@craddm craddm deleted the fix-external-dns-queries branch September 11, 2023 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

External DNS script using incorrect VM name Configuring external DNS resolution for SRDs fails
2 participants